home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Tools (InfoMagic)
/
Internet Tools.iso
/
dos_win
/
winsock
/
maillist
/
94-05.Z
/
94-05
/
000168_news@bigblue.oit.unc.edu_Thu May 12 19:04:03 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1994-05-31
|
7KB
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
id AA17575; Thu, 12 May 1994 18:45:40 -0400
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
id AA35639; Thu, 12 May 1994 18:26:22 -0400
Received: from GATEWAY by bigblue with netnews
for winsock@sunsite.unc.edu (winsock@sunsite.unc.edu)
To: winsock@sunsite.unc.edu
Date: Thu, 12 May 1994 19:04:03 GMT
From: arnstein@netcom.com (David Arnstein)
Message-Id: <arnsteinCppEAr.L72@netcom.com>
Organization: My Own Internet Account!
Sender: ses
References: <matt.10.2DCAB5B1@sc1.tamu.edu>, <2qrdb3$lr@bmerha64.bnr.ca>, <1994May12.155317.3383@megatek.com>
Reply-To: arnstein@netcom.com
Subject: Re: 32 bit access with SCSI no available. Hunh? was Re: Win Mosaic alpha 4 (my fix)
In article <1994May12.155317.3383@megatek.com>,
Antti Tirronen <ajt@megatek.com> wrote:
>When I had both IDE and SCSI disks installed, I had windows on the IDE disk
>and it was happy (and faster) with its 32-bit mode. I haven't yet taken the
>time to try to figure out how to get that back, now that I got rid of the IDE
>in favor of an all out SCSI system.
You've discovered the annoying fact that under Windows 3.1 and WFWG 3.11, SCSI
disk I/O is SLOW, SLOW, SLOW. This is because Windows 3.1 won't do 32-bit disk
access for (almost all) SCSI host adapters.
As a result, each time SCSI I/O occurs, Windows must switch from 32-bit
protected mode to real mode, and run code out of your SCSI host adapters ROM
BIOS. Doubly slow!
If you had 32-bit disk access going, Windows would run the code (32-bit disk
access driver) in protected mode, without touching your SCSI BIOS.
Only Future Domain host adapters are supplied with a driver that permits 32-bit
disk access from Windows. This driver does not work with WFWG 3.11 and
besides, if you do use this driver, you may have to disable 32-bit disk access
for your IDE drive(s).
Windows 3.1 users:
*** J U S T S A Y N O T O S C S I ***
--
David Arnstein | What do you mean, "get a life"?
arnstein@netcom.com | This *is* my life!
From news@bigblue.oit.unc.edu Thu May 12 19:08:47 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
id AA17563; Thu, 12 May 1994 18:45:34 -0400
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
id AA26616; Thu, 12 May 1994 18:18:43 -0400
Received: from GATEWAY by bigblue with netnews
for winsock@sunsite.unc.edu (winsock@sunsite.unc.edu)
To: winsock@sunsite.unc.edu
Date: Thu, 12 May 1994 19:08:47 GMT
From: yon@world.std.com (David A Yon)
Message-Id: <CppEIo.9Kn@world.std.com>
Organization: The World Public Access UNIX, Brookline, MA
Sender: ses
Subject: Decent TELNET library for WinSock programmers?
Has anyone found a decent vendor (or even better, public-domain)
which provides a library to provide TELNET connections? I'm looking to add
the ability to push data over a TELNET connection to my Windows program.
Here are my requirements:
1) Works using WINSOCK
2) Packaged as a DLL or LIB
3) Minimal (or no) redistribution limitations
4) Provides simple interface to open a TELNET connection, read/write data
to the connection, close the connection.
I've found several implementations, but none to my liking:
1) Distinct has a good solution, but wants $50/copy to redistribute telnet.dll!
2) GCP++ costs $1000 for the SDK and redistribution rights, and has a hokey
"server" EXE which your program communicates with.
3) There's an SDK for Chameleon, but the salesperson wasn't real helpful in
getting my questions answered.
Has anyone used the Chameleon SDK? If so, is there the equivalent
of a "TELNET.DLL" which gives me a high-level API to telnet connections?
Can I freely redistribute that DLL? Any other vendors I should know about?
Thanks in advance for any info...
David
yon@world.std.com
From news@bigblue.oit.unc.edu Thu May 12 21:18:36 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
id AB17604; Thu, 12 May 1994 18:45:57 -0400
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
id AA35837; Thu, 12 May 1994 18:21:25 -0400
Received: from GATEWAY by bigblue with netnews
for winsock@sunsite.unc.edu (winsock@sunsite.unc.edu)
To: winsock@sunsite.unc.edu
Date: Thu, 12 May 1994 21:18:36 GMT
From: hutton@rintintin.colorado.edu
Message-Id: <CppKJ0.H5p@cnsnews.Colorado.EDU>
Organization: University of Colorado - Boulder [CNS Small Systems]
Sender: ses
References: <2qrjkp$quf@usenet.srv.cis.pitt.edu>
Reply-To: hutton@rintintin.colorado.edu
Subject: Re: IBM TCP/IP and Trumpet Winsock
In comp.os.os2.networking.tcp-ip, David J Birnbaum writes:
>I have succeeded in running WinMosaic through Trumpet tcpman.exe over a
>slip connection, but I can't get it to work on an ethernet-connected
>machine. Can anyone advise?
[snip]
>> Error - Unable to locate WINPKT or PKTDRV virtual packet driver
>
>If I had to guess, I would guess that I'm not loading a packet driver
>properly or setting an address properly or something like that. But I
>didn't install my own network card and I'm not sure where to look for
>the information.
When the TCP/IP for OS/2 kit is installed and running, OS/2 uses the TCP/IP
stack and doesn't allow Dos or Windows to access the stack directly. If you disable
the OS/2 TCP/IP (and NetWare Requester, if that's loaded) and then try to load
a packet driver, you should be able to use the ethernet adapter. You should also be
able to use a Winsock dll.
Quoting Gilbert-Howard@yale.edu:
The Trumpet WINSOCK package would run under OS/2 2.x WINOS2 if the
LAN adapter is not defined to OS/2, there is no OS/2 LAN support, there is
no NDIS (LAPS) driver. Then one DOS VDM could grab it exclusively and run
one program (such as Trumpet WINSOCK). Architecturally, it may be possible
to run OS/2 TCP on one Ethernet card and Trumpet WINSOCK on a second
card.
Trumpet WINSOCK will not run in a DOS VDM under the IBM TCP/IP for OS/2
because IBM TCP/IP does not present a "virtual packet driver" that TCPMAN
would understand. The DOS/WIN Access Kit provides a virtual device driver
that allows DOS/WIN programs to "handoff" TCP API calls to the real TCP running
under OS/2. It is also not possible for a real packet driver running in the DOS
environment to share the same Ethernet card with NDIS running in OS/2.
Willie Hutton
---------------------------------------------------------------------
William Hutton The opinions expressed are my
University of Colorado - Boulder own and not my employers. If
CNS Small Systems you don't like it, tough luck.
---------------------------------------------------------------------